The command-center app carries 210 route files across roughly fifteen top-level groups, and its information architecture mirrors the engineering estate: cells, services, kernels, agents. An operator does not arrive with a cell in mind. They arrive with a decision to make.
The /command-center slice already solved the hard part — tri-state reads, trace ids on every panel, explicit [not-wired] notes, role-gated mutations. The proposal below keeps that discipline verbatim and rebuilds the shell around it.
app/, plus 317 more below depth three. No operator can hold this map./, /dashboard, /dashboard/modern, /command-center, /operate, /mizoki.app/page.tsx. Four other pages clear 30KB. Layout, fetching, and copy all in one file./command-center. This is the seed, not a rewrite.Not a metric wall. The first thing an operator sees is the set of decisions waiting on a human, ordered by what the platform cannot do without them.
One page that answers three questions in order: where is this in the pathway, why does the platform believe it, and what happens the moment I press approve.
The existing app has five separate SRPVDAL views. One is enough if it tells the truth: each phase reports live, unavailable with a reason, or not-wired, and the three never blend.
Nothing is deleted. Every existing page becomes a tab, a panel, or a deep link inside one of five destinations, and the duplicate homes resolve to the inbox.